Skip to content
This repository was archived by the owner on Mar 26, 2026. It is now read-only.

docs: update CLAUDE.md for OpenDispatch rebrand consistency#290

Merged
jsell-rh merged 1 commit intojsell-rh:mainfrom
tiwillia-ai-bot:docs/update-claude-md-branding
Mar 23, 2026
Merged

docs: update CLAUDE.md for OpenDispatch rebrand consistency#290
jsell-rh merged 1 commit intojsell-rh:mainfrom
tiwillia-ai-bot:docs/update-claude-md-branding

Conversation

@tiwillia-ai-bot
Copy link
Copy Markdown

Summary

Updates CLAUDE.md to align with the OpenDispatch rebrand and fix outdated/incomplete documentation.

Changes

  • Vite proxy list: Added missing endpoints (/personas, /mcp, /settings) to match current vite.config.ts
  • MCP tool references: Changed boss-devodis-dev to align with rebrand
  • Example space names: Updated from "Agent Boss Dev" → "My Space" for consistency with rebrand
  • Backward compatibility note: Added documentation for legacy BOSS_* environment variables
  • MCP naming clarification: Added note explaining odis-mcp rebrand and why boss-observe retains legacy naming
  • Example names: Standardized example agent/session names for clarity

Verification

Fixes inconsistencies identified during CLAUDE.md accuracy review.

- Update Vite proxy list to include /personas, /mcp, /settings
- Change boss-dev → odis-dev for MCP tool references
- Update example space names (Agent Boss Dev → My Space)
- Add backward compatibility note for BOSS_* environment variables
- Add note clarifying odis-mcp rebrand and boss-observe legacy naming
- Standardize example agent/session names for clarity
@jsell-rh jsell-rh merged commit 11d87fd into jsell-rh:main Mar 23, 2026
3 checks passed
jsell-rh added a commit that referenced this pull request Mar 23, 2026
…-setup.sh

Aligns scripts with CLAUDE.md docs (PR #290). MCP server name changed from
boss-dev to odis-dev in the generated JSON config, allowed tools list, and
output messages. BOSS_API_TOKEN/BOSS_MCP_URL env vars kept as fallbacks for
backward compatibility (prefer ODIS_API_TOKEN/ODIS_MCP_URL going forward).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jsell-rh added a commit that referenced this pull request Mar 23, 2026
Aligns scripts with CLAUDE.md docs (PR #290). MCP server name changed from
boss-dev to odis-dev in the generated JSON config, allowed tools list, and
output messages. BOSS_API_TOKEN/BOSS_MCP_URL env vars kept as fallbacks for
backward compatibility (prefer ODIS_API_TOKEN/ODIS_MCP_URL going forward).

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
jsell-rh added a commit that referenced this pull request Mar 24, 2026
…r Conversations (#292)

* fix(scripts): rebrand boss-dev → odis-dev in spawn-dev-agent.sh + dev-setup.sh

Aligns scripts with CLAUDE.md docs (PR #290). MCP server name changed from
boss-dev to odis-dev in the generated JSON config, allowed tools list, and
output messages. BOSS_API_TOKEN/BOSS_MCP_URL env vars kept as fallbacks for
backward compatibility (prefer ODIS_API_TOKEN/ODIS_MCP_URL going forward).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix(ui): operator messages appear in agent conversations instead of Your Conversations

Root cause: both 'boss' (legacy) and 'operator' agents have agent_type='human' in the
DB. operatorName computed returned whichever was found first via Object.entries, which
is insertion-order. In spaces where 'boss' was created first, operatorName='boss'.

Consequences when operatorName='boss' but messages use 'operator':
- Conversations with 'operator' participant went to Agent Conversations section
- composeRecipient was null for those conversations (no compose box shown)
- Unread acks used wrong agent name

Fix: collect ALL human agents into humanAgentNames Set. Use it for:
- isOperatorConversation: any participant that is a human agent
- composeRecipient: any participant that is NOT a human agent
- unreadCount / ackOperatorMessages: any human-agent recipient
- operatorName: prefer 'operator' (canonical) over legacy 'boss'

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix(messages): canonicalize sender name to prevent duplicate conversation threads

When agents use different capitalizations (e.g. "CEO" vs "ceo"), messages were stored
with the raw sender name, creating separate conversation threads in the UI for what
should be a single conversation.

Both handleAgentMessage (HTTP) and send_message (MCP tool) now call resolveAgentName
on the sender after the space is loaded, mapping to the canonical stored name if the
sender is a known agent. Unknown senders keep their original name unchanged.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants